Hi, I'm having difficulties with Out of office emails being sent to external emal adresses. The returnpath header of the message is empty (<>) and gets dropped by our provider. I understand this is a feature in MS exchange 2007. I thought I would resolve it using Transport Rules and thus created the following rule : Apply rule to messages From users Inside the organization and sent to users Outside the organization and when the Subject field contains Out of Office Set Return-Path with test@mydomain.com After that I rebooted the server, and thus the SMTP service but still the header doesn't get filled. Any Ideas? Thanks in advance. Pieter

might be helpful... http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_23148007.html "last one"

On Thu, 28 Oct 2010 08:23:03 +0000, Pieter VdB wrote: >I'm having difficulties with Out of office emails being sent to external emal adresses. The returnpath header of the message is empty (<>) and gets dropped by our provider. Your provider is wrong. I'm guessing you're using some kind of residential service instead of a business service? It's not usual for a residential customers to be running server software. >I understand this is a feature in MS exchange 2007. Sort of . . . it's the way things are supposed to work (check the relevant RFCs). DSNs are supposed to be sent using the "null address" do they don't create message loops. Other types of messages shouldn't receive DSNs (e.g. a large distribution list shouldn't distribute a DSN to the entire membership). >I thought I would resolve it using Transport Rules and thus created the following rule : > >Apply rule to messages From users Inside the organization and sent to users Outside the organization and when the Subject field contains Out of Office Set Return-Path with test@mydomain.com > >After that I rebooted the server, and thus the SMTP service but still the header doesn't get filled. > >Any Ideas? --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

On Thu, 28 Oct 2010 08:23:03 +0000, Pieter VdB wrote: Your provider is wrong. I'm guessing you're using some kind of residential service instead of a business service? It's not usual for a residential customers to be running server software. We have a "corporate internet" DSL connection, so one would expect things to run smoothly... Anyway, I have contacted the provider and they will "check it". Thank you for the replies, and when i get feedback I will post it here. Pieter

might be helpful... http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_23148007.html "last one" Thanks, but i have to get an account to view the answer, even if i scroll down (which usually works :) ) Pieter

On Fri, 29 Oct 2010 06:59:35 +0000, Pieter VdB wrote: >On Thu, 28 Oct 2010 08:23:03 +0000, Pieter VdB wrote: Your provider is wrong. I'm guessing you're using some kind of residential service instead of a business service? It's not usual for a residential customers to be running server software. > >We have a "corporate internet" DSL connection, so one would expect things to run smoothly... And the *would* if the provider understood the way thing are supposed to work. :-) http://www.ietf.org/rfc/rfc2298.txt?number=2298 Section "3." . . . The envelope sender address (i.e., SMTP MAIL FROM) of the MDN MUST be null (<>), specifying that no Delivery Status Notification messages or other messages indicating successful or unsuccessful delivery are to be sent in response to an MDN. >Anyway, I have contacted the provider and they will "check it". Provide them with the link to the RFC. :-) --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

On Fri, 29 Oct 2010 06:59:35 +0000, Pieter VdB wrote: >On Thu, 28 Oct 2010 08:23:03 +0000, Pieter VdB wrote: Your provider is wrong. I'm guessing you're using some kind of residential service instead of a business service? It's not usual for a residential customers to be running server software. > >We have a "corporate internet" DSL connection, so one would expect things to run smoothly... And the *would* if the provider understood the way thing are supposed to work. :-) http://www.ietf.org/rfc/rfc2298.txt?number=2298 Section "3." . . . The envelope sender address (i.e., SMTP MAIL FROM) of the MDN MUST be null (<>), specifying that no Delivery Status Notification messages or other messages indicating successful or unsuccessful delivery are to be sent in response to an MDN. >Anyway, I have contacted the provider and they will "check it". Provide them with the link to the RFC. :-) --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP My idiot provider is being stubborn, saying that they can do nothing about it and we should adjust our mailserver settings. I tried to explain that this is just not possible but they refuse to provide any help... I'll try to contact our account manager about this, I'll keep you posted. Kind regards, Pieter